Implement the "limit" modifier for binding #2051
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sometimes a user wants to map/bind procs by an object type, but needs to limit the number of procs bound to any particular object to some arbitrary number (i.e., not the number of available CPUs on the object). Example might be to map/bind to a cache level, but limit the number of procs on any given cache to some smaller number before moving to the next cache. Docs were updated to explain this in a prior commit. Signed-off-by: Ralph Castain <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes a user wants to map/bind procs by an object type, but needs to limit the number of procs bound to any particular object to some arbitrary number (i.e., not the number of available CPUs on the object). Example might be to map/bind to a cache level, but limit the number of procs on any given cache to some smaller number before moving to the next cache.
Docs were updated to explain this in a prior commit.